Correctly check content type #114
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #114 +/- ##
==========================================
- Coverage 77.59% 77.42% -0.17%
==========================================
Files 41 41
Lines 4342 4328 -14
Branches 841 838 -3
==========================================
- Hits 3369 3351 -18
- Misses 709 712 +3
- Partials 264 265 +1
Continue to review full report at Codecov.
|
rohe
approved these changes
Mar 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current we log a warning if we receive
Content-Type: application/json; charset=utf-8, but wantapplication/json. This PR fixes this.N.B. a charset option for JSON content is moot, since only utf8 may be used.